---
title: "Workflows"
description: "Workflows trigger agents on a schedule or when events occur."
---


<Info>

  What is a Workflow?

  A Workflow automatically runs an Agent on a repository when:
  - A schedule is reached (cron)
  - An event occurs (webhook, e.g. GitHub PR)

  Use Workflows for recurring or event-driven tasks like:
  - Daily vulnerability scans
  - Weekly changelog generation
  - Reacting to new pull requests or Sentry alerts

</Info>

---

## Creating a Workflow

<Steps>

  <Step title="Start from scratch or a template">

    In Mission Control → Workflows, create a [new workflow](https://hub.continue.dev/workflows/new).
<AccordionGroup>

  <Accordion title="Start with a Blank Workflow">
    Create a workflow from scratch by clicking Create Workflow.  
    You'll choose the repository, agent, trigger type, and schedule or webhook.
  </Accordion>

  <Accordion title="Use a Workflow Template">
    Select any of the “Try these Workflows” cards such as:
    - _Update agents.md_
    - _Draft Changelog Updates_
    - _Solve Snyk Vulnerabilities_

    Templates preload the recommended agent and schedule so you can customize and run them quickly.
  </Accordion>

</AccordionGroup>

  </Step>

  <Step title="Name the Workflow">

    Give your Workflow a clear, descriptive name.

    Examples:
    - `Morning status check`
    - `Weekly changelog draft`
    - `Daily Snyk vulnerability scan`

  </Step>

  <Step title="Select Repository & Agent">

    Choose:

    - Repository – the codebase the Agent will run against  
    - Agent – the configured Agent (model, rules, tools, prompt) that should perform the work

    <Tip>
      Need a new Agent? Create one in [Mission Control → Agents](https://hub.continue.dev/new?type=agent), then return to this screen.
    </Tip>

  </Step>

  <Step title="Choose Trigger Type">

    Pick how this Workflow should run:

    - Cron – run on a schedule (daily, weekly, hourly, custom)  
    - Webhook – run when an external system sends a request (e.g. GitHub PR event)

  </Step>

  <Step title="Configure the Trigger">

    <AccordionGroup>

      <Accordion title="Cron Workflow">

        For scheduled Workflows:

        1. Select Cron as the trigger type  
        2. Choose a schedule:
           - Common presets (e.g. weekdays at 9 AM UTC)
           - Hourly, Daily, Weekly, Monthly
           - Or define a Custom expression  
        3. (Optional) Add additional instructions for this Workflow run in the text area.

        Example use cases:
        - Run a morning status check on your repo every weekday  
        - Refactor React components once per week  
        - Generate a weekly changelog from recent commits  

      </Accordion>

      <Accordion title="Webhook Workflow">

        For event-based Workflows:

        1. Select Webhook as the trigger type  
        2. (Optional) Set a Secret Header (e.g. `X-Webhook-Secret`)  
        3. (Optional) Set a Secret Value (token your external system must send)  

        You’ll receive a webhook URL to call from:
        - GitHub Actions
        - GitHub webhooks
        - CI/CD pipelines
        - Any external system that can send HTTP requests

        Example use cases:
        - Run an Agent whenever a pull request is opened  
        - Kick off a workflow when Snyk or Sentry detects an issue  

      </Accordion>

    </AccordionGroup>

  </Step>

  <Step title="Create the Workflow">

    Click Create Cron Workflow or Create Webhook Workflow, depending on your trigger type.

    Your Workflow will now appear in the Workflows list and begin running based on its configured schedule or events.

  </Step>

</Steps>

## Monitoring Workflow Runs

Workflow runs show up just like Tasks:

- Each execution creates a Session  
- Workflows appear in your Inbox  
- You can open the detail view to see the summary, diff, and logs.

<CardGroup>
  <Card title="Create a Workflow Now" icon="workflow" href="https://hub.continue.dev/workflows">
  </Card>

  <Card title="Add an Integration" icon="workflow" href="/mission-control/integrations">
    Connect GitHub, Slack, and Sentry for richer triggers and actions.
  </Card>

</CardGroup>